I am following this page and using the same payload to create the new Knowledge base https://docs.vapi.ai/knowledge-base here is the payload but giving error "message": "Invalid Knowledge Base Details. Failed to create trieve dataset", "error": "Bad Request", { "name": "v2", "provider": "trieve", "searchPlan": { "searchType": "semantic", "topK": 3, "removeStopWords": true, "scoreThreshold": 0.7 }, "createPlan": { "type": "create", "chunkPlans": [ { "fileIds": ["a0f1a569-55ed-4ce2-8972-2067243e3ef0"], "websites": [], "targetSplitsPerChunk": 50, "splitDelimiters": [".!?\n"], "rebalanceChunks": true } ] } }

Please check that the organization you are trying to create the Knowledge base under exists If your account does not have the right privileges, maybe "Not found" error can be appeared

@Mr.Traveller I have everything checked and that correct but still this issue

hmm. strange..

I am not sure it looks like issue with the knowledge base creation

@mauryasumit If you create a dataset in trieve and upload your kb files directly on trieve, generate new trieve api key and paste that in credential provider in Vapi, you can then import your kb to Vapi by making a post request to Vapi api knowledge-base route JSON: { "name": “name your kb file”, "provider": "trieve", "searchPlan": { "scoreThreshold": 0.2, "searchType": "semantic" }, "createPlan": { "type": "import", "providerId": "" } } Doc for detailed breakdown: https://docs.vapi.ai/knowledge-base/integrating-with-trieve

That's fine but I was planning to use vapi directly for creation of KB

VAPIs handling of knowledge bases is terrible. First they broke the KB UI, forcing everyone to upload their KB using their API. Then they broke the API, forcing everyone to go to Trieve. What kind of professional product development is this?

Not able to save api key in provider stating Internal error, are you able to save new key?

@samuelpjackson do know of any guide on how to create a dataset on trieve so it can be imported in VAPI?

@mauryasumit Is this resolved for you? If not, let me know where you’re blocked. we've noticed that when using our API key for creating a knowledge base, the request sometimes fails with a 403 error. The problem seems to be related to how our system create plan syncs with Trieve, causing issues when the same key is used repeatedly. temporary solution: For now, please use your own Trieve dataset for the knowledge base. This workaround avoids the create plan syncing issue and should let the KB process go through without errors.

Just did it. Still does not work. I can not import the dataset and not even show the list of datasets. I tried all sorts of API keys in the provider crendentials for trieve nothing seems to work. It looks like the connection to trieve in general is not working

Here's an example of how to setup the dataset in Trieve: And then I used this POST request in Postman:

POST https://api.vapi.ai/knowledge-base
Headers:
Authorization: Bearer {{vapi_api_key}}

Body:
{
  "name": "{{knowledge_base_name}}",
  "provider": "trieve",
  "searchPlan": {
    "scoreThreshold": 0.2,
    "searchType": "semantic"
  },
  "createPlan": {
    "type": "import",
    "providerId": "{{dataset_id}}"
  }
}

so now it's official that we need to first upload the file on

trieve

then use that on VAPI

@mauryasumit deleting your message because of API keys involved. Your curl request is valid it's just that you have use right private API key, your using your public key.